极限工况下的管网“互联互通”改进方案

在全国天然气管道“主干互联、区域成网”(以下简称“互联互通”)基础格局逐渐形成的背景下,天然气管网规模日益扩大、管道分支和气源增加,并且分布不集中、输送方向可变,使得输气方案更加灵活,可以更好地解决某些地域的供气紧张问题;但受现有站场和设备的限制,暂不能满足某些多线组合极限工况,使得“互联互通”的初衷难以全部实现。为了使得现有的各输气干线在实现“互联互通”之后可以满足更多的多线组合工况,在分析“互联互通”背景下M管网工况变化的基础上,研发了可以进行水力仿真和压气站方案制订的计算软件,并对3种极限工况下的不同输气量情况进行了可行性试算,进而基于试算结果提出了相应的管网改进建议。研究结果表明:(1)经验证,软件计算误差满足要求;(2)在M管道某处增设压气站或在某些输气站场配置压缩机组;(3) M管网改进调整后,可以完成大部分的多线组合极限工况,真正实现“互联互通”的输气方案。结论认为,该研究成果有助于推进全国天然气管网早日实现“互联互通”。     

Deployment of a cloud pipeline for real-time visual inspection using fast streaming high-definition images

We investigate the challenges of building an end-to-end cloud pipeline for real-time intelligent visual inspection system for use in automotive manufacturing. Current methods of visual detection in automotive assembly are highly labor intensive, and thus prone to errors. An automated process is sought that can operate within the real-time constraints of the assembly line and can reduce errors. Components of the cloud pipeline include capture of a large set of high-definition images from a camera setup at the assembly location, transfer and storage of the images as needed, execution of object detection, and notification to a human operator when a fault is detected. The end-to-end execution must complete within a fixed time frame before the next car arrives in the assembly line. In this article, we report the design, development, and experimental evaluation of the tradeoffs of performance, accuracy, and scalability for a cloud system.     

基于启发式BP算法的软件缺陷预测模型

针对软件缺陷预测时缺陷数据集中存在的类别分布不平衡问题，结合上采样算法SMOTE与Edited Nearest Neighbor (ENN) 数据清洗策略，提出了一种基于启发式BP神经网络算法的软件缺陷预测模型。模型中采用上采样算法SMOTE增加少数类样本以改善项目中的数据不平衡状况，并针对采样后数据噪声问题进行ENN数据清洗，结合基于启发式学习的模拟退火算法改进四层BP神经网络后建立分类预测模型，在AEEEM数据库上使用交叉验证对提出的方案进行性能评估，结果表明所提出的算法能够有效提高模型在预测类不平衡数据时的分类准确度。     

干湿联合冷却塔冷却节水分析软件开发及应用

为实现对干湿联合冷却塔冷却特性、节水特性的综合分析，编制干湿联合冷却塔校核计算流程，基于Visual Studio开发平台，本文开发了干湿联合冷却塔冷却节水特性分析优化软件。通过对某在运干湿联合冷却塔进行冷却节水特性计算，验证了所开发软件计算结果的准确性；在消雾节水计算结果基础上，对标干湿联合消雾冷却塔验收测试规程，生成其成雾频率曲线、耗水量曲线、塔雾指数、冷却特性曲线，综合分析其消雾特性、节水特性及冷却特性，从而确定了干湿联合冷却塔的最佳运行工况。同时运用所开发软件对比分析了某冷却塔设计干段散热面积对其消雾特性、节水特性及冷却特性的耦合影响，并分析了百叶窗开度对干湿联合冷却塔性能的影响，为干湿联合冷却塔的运行优化和设计优化提供了工具性软件支持。     

新型硫酸法C_4烷基化工艺的模拟

提出了一种新型硫酸法C4烷基化生产工艺,丁烯原料在气相状态下进入反应器,与液相异丁烷、浓硫酸混合后,部分丁烯溶于液相,在液相中进行反应;通过控制反应器的压力,部分液相吸收反应热而汽化,使反应温度基本稳定;经气液分离、酸烃分离及产品分馏后,气相丁烯、异丁烷、浓硫酸分别构成循环。采用Aspen Plus过程模拟软件对新工艺过程进行模拟计算的结果表明,在反应器进口压力0.2 MPa、压降4.5 k Pa的条件下,反应器进出口温度均在7.2℃左右,可通过调节反应器压力实现温度的控制;反应器进口液相中烷烯质量比为145∶1,可减少副反应的发生;与传统硫酸法C4烷基化工艺相比,新工艺耗电量可降低30%。     

尾矿库排水管封堵技术及相关事故处理

当尾矿库库底排水管强度不能满足坝体加高的承载要求，且无法进行加固或在使用过程中出现损坏迹象时，均应对其进行封堵。排水管的封堵位置与封堵长度关系到尾矿库的安全运行，必须高度重视，防止留下安全隐患。该文结合某矿山工程事故案例，提出了排水管封堵技术要求以及因排水管承载能力不足导致的事故处理方法，为类似尾矿库工程提供参考。     

An industrial case study on variability handling in large enterprise software systems

ContextEnterprise software systems (e.g., enterprise resource planning software) are often deployed in different contexts (e.g., different organizations or different business units or branches of one organization). However, even though organizations, business units or branches have the same or similar business goals, they may differ in how they achieve these goals. Thus, many enterprise software systems are subject to variability and adapted depending on the context in which they are used.ObjectiveOur goal is to provide a snapshot of variability in large scale enterprise software systems. We aim at understanding the types of variability that occur in large industrial enterprise software systems. Furthermore, we aim at identifying how variability is handled in such systems.MethodWe performed an exploratory case study in two large software organizations, involving two large enterprise software systems. Data were collected through interviews and document analysis. Data were analyzed following a grounded theory approach.ResultsWe identified seven types of variability (e.g., functionality, infrastructure) and eight mechanisms to handle variability (e.g., add-ons, code switches).ConclusionsWe provide generic types for classifying variability in enterprise software systems, and reusable mechanisms for handling such variability. Some variability types and handling mechanisms for enterprise software systems found in the real world extend existing concepts and theories. Others confirm findings from previous research literature on variability in software in general and are therefore not specific to enterprise software systems. Our findings also offer a theoretical foundation for describing variability handling in practice. Future work needs to provide more evaluations of the theoretical foundations, and refine variability handling mechanisms into more detailed practices.     

单汽泡沸腾过程数值模拟的研究

利用Comsol Multiphysics软件中的Level Set方法对单汽泡沸腾过程进行了模拟,建立了微细结构网格,给出了边界条件,求解了质量、动量、能量和Level Set方程,得到了正确的模拟结果。分析了单汽泡沸腾过程中相含率、压力场、速度场和温度场随时间的变化规律;考察了接触角和壁面效应对汽泡脱离直径和汽泡生长周期的影响。模拟结果表明,当接触角小于12°时,汽泡脱离直径维持不变;当接触角大于12°时,接触角越大,汽泡脱离直径越大。汽泡生长周期随接触角的增大而延长。当加热装置的直径小于汽泡脱离直径时,汽泡受壁面效应的影响不易脱离;当加热装置的直径大于汽泡脱离直径时,汽泡脱离直径不随加热装置直径的增大而变化;汽泡生长周期随加热装置直径的增大而缩短。     

A data‐centric framework for debugging highly parallel applications

Contemporary parallel debuggers allow users to control more than one processing thread while supporting the same examination and visualisation operations of that of sequential debuggers. This approach restricts the use of parallel debuggers when it comes to large scale scientific applications run across hundreds of thousands compute cores. First, manually observing the runtime data to detect error becomes impractical because the data is too big. Second, performing expensive but useful debugging operations becomes infeasible as the computational codes become more complex, involving larger data structures, and as the machines become larger. This study explores the idea of a data‐centric debugging approach, which could be used to make parallel debuggers more powerful. It discusses the use of ad hoc debug‐time assertions that allow a user to reason about the state of a parallel computation. These assertions support the verification and validation of program state at runtime as a whole rather than focusing on that of only a single process state. Furthermore, the debugger's performance can be improved by exploiting the underlying parallel platform because the available compute cores can execute parallel debugging functions, while a program is idling at a breakpoint. We demonstrate the system with several case studies and evaluate the performance of the tool on a 20 000 cores Cray XE6. Copyright © 2013 John Wiley & Sons, Ltd.